Skip to content

Conversation

@fanzeyi
Copy link
Member

@fanzeyi fanzeyi commented Nov 25, 2025

As #222 demonstrated, it is possible for us to introduce dependency to a newer version of a dependency package without breaking our CI.

This PR makes our GitHub Action to test for both lowest-direct and highest package resolution strategy so we can make sure the lower bounds we write in our package dependency still work.

Test Plan

GitHub Action on this PR still passes.

PEP 735 defines dependency groups which is a bit different from optional
dependencies -- notablely this dependency information is not exported as part of
the package metadata. For dependencies needed for testing purposes, we can use
dependency groups and having optional dependencies to focus on providing
customizations for the users.
@fanzeyi fanzeyi force-pushed the push-rorwpxntzsnw branch 14 times, most recently from f7a8152 to d41665b Compare November 26, 2025 00:19
@fanzeyi fanzeyi changed the title test chore: start testing both lowest-direct and highest package resolution strategy Nov 26, 2025
@fanzeyi fanzeyi marked this pull request as ready for review November 26, 2025 00:22
@fanzeyi fanzeyi requested a review from aravind-segu November 26, 2025 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant